Hi!

I found the same problem (or similar), but as it was generated
by a (faulty) while loop, it took some times for me to find it... I
think (but I did not test) that feeding a 'nan' or an 'inf' (as reported
by the #warning stream) to pov jams the parser in the auto-bounding
process. I believe it is the auto-bounding because (1) that is the status
displayed in the status bar when pov jams; (2) it did not happened
when the auto-bounding wasn't needed (number of objects under
the auto-bounding treshold).

I think the generation of such values should be trapped (weren't they in
earlier versions? I can't remenber...). Or they could be trapped when used
in an object (as degenarated shapes are).

Of course this isn't really a bug: we should try to avoid creating such
values. But it would be more confortable if pov handled them better.



Povingly,


Philippe

Post a reply to this message